-
Notifications
You must be signed in to change notification settings - Fork 242
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: cilium scale pipeline #2085
Conversation
b783de2
to
e611c08
Compare
…re-container-networking into camryn/ciliumscaletest
#!/bin/bash | ||
# find the nodes with netperf pods and assign test vars | ||
node_found=0 | ||
for node in $(kubectl get nodes -o name); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can limit this result to three if we use the label selector netperf=true
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, in label-nodes.sh I cut off the netperf=true
labeling once 3 nodes have it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work Camryn! Lgtm.
…etworking into camryn/ciliumscaletest
…etworking into camryn/ciliumscaletest
…re-container-networking into camryn/ciliumscaletest
Reason for Change:
This PR creates a new cilium scale pipeline to test a cluster at 1000 nodes. It adopts NPM's existing scale test to create nginx deployments and services, and it uses the existing connectivity test. It uses apachebench and netperf to test the throughput and gathers cpu memory usage. The results are published as pipeline artifacts. We will reuse the same cluster for all builds, and at the end of each run the cluster is scaled back down to 5 nodes.
Issue Fixed:
Requirements:
Notes: